Don't strip semicolons after closing parentheses #333
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthiasmullie
force-pushed
the
master
branch
5 times, most recently
from
85ee174 to
227f190
Compare
|
@pcfreak30 sup man 😄 |
matthiasmullie
force-pushed
the
master
branch
3 times, most recently
from
949e01d to
51d1aa4
Compare
matthiasmullie
force-pushed
the
master
branch
2 times, most recently
from
9ddadb8 to
4c4ecee
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The regex to clean up semi-colons does not take into account that it may be after a function call.
A small sample from an already minified bundle is
break"!==n(););},Ur). Adding a negative lookbehind fixes this.